Server information handling system NFC ticket management and fault storage

ABSTRACT

Server information handling system deployment and maintenance is enhanced with automated trouble ticket generation at a mobile telephone through an NFC transaction with a management controller. NFC transactions coordinate authorization for replacement component installation and server information handling system replacement. In one embodiment, a bezel includes an NFC device that interfaces with a management controller and stores configuration information to aid installation of replacement server information handling systems in the event of a system failure. A back-up battery provides power to an NFC support circuit that stores fault codes detected by the management controller so that fault codes are available during management controller failures.

CONTINUING DATA

This application is a continuation-in-part of U.S. patent applicationSer. No. 14/259,574, filed Apr. 23, 2014, entitled “NFC Communicationwith an Information Handling System Supplemented by a ManagementController and Advertised virtual Tag Memory,” by Shawn Dube and Syed S.Ahmed, which includes exemplary systems and methods and is incorporatedby reference in its entirety.

CROSS REFERENCE TO RELATED APPLICATION

U.S. patent application Ser. No. 14/272,805, entitled “ServerInformation Handling System NFC Ticket Management And Fault Storage” byinventors Kevin D. Terwilliger, Travis E. Taylor, Syed S. Ahmed, andJohn R. Palmer, filed on May 8, 2014, describes exemplary methods andsystems and is incorporated by reference in its entirety.

BACKGROUND OF THE INVENTION

Field of the Invention

The present invention relates in general to the field of serverinformation handling system management, and more particularly to aserver information handling system NFC ticket management and faultstorage.

Description of the Related Art

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option available to users is information handling systems. Aninformation handling system generally processes, compiles, stores,and/or communicates information or data for business, personal, or otherpurposes thereby allowing users to take advantage of the value of theinformation. Because technology and information handling needs andrequirements vary between different users or applications, informationhandling systems may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in informationhandling systems allow for information handling systems to be general orconfigured for a specific user or specific use such as financialtransaction processing, airline reservations, enterprise data storage,or global communications. In addition, information handling systems mayinclude a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more computer systems, data storage systems, andnetworking systems.

Server information handling systems are typically centrally located in adata center that has specialized infrastructure to provide networking,power and cooling resources. Often, plural server information handlingsystems are stacked in racks that have plural slots to provideinfrastructure interfaces. For example, a typical server rack includesmultiple power supplies and a communication switch that each supportsserver information handling systems installed in slots of the rack.Racks are disposed in a room having a controlled environment, such aswith cooling air vented near each rack. The server information handlingsystems typically include a baseboard management controller (BMC) thatallows remote support operations, such as network-based power-up,power-down, component monitoring, firmware updates and other managementoperations. Generally, BMC's communicate with administrative toolsthrough an out-of-band management network that is separate from thenetworks that the server information handling systems functionallyserve. For instance, a server information handling system serves clientrequests responsive to enterprise functions performed over the Internetthrough a primary network interface and is managed by administrativenetwork tools through a secondary management network.

In modern cloud networking configurations, physical server informationhandling systems provide physical processing resources that supportvirtual processing devices, such as virtual machines. As a result, in agiven data center, a physical mapping of enterprise functions to thephysical machine performing the enterprise functions is often notimmediately available and frequently changing. In effect, the physicalmaintenance of server information handling systems is separate from themaintenance of virtual machines that run over the physical systems. As aphysical server information handling system runs into difficultyexecuting an enterprise function, such as due to processing load orfailure of components, the enterprise function virtual machine migratesto different physical resources. Although cloud networking helps toachieve efficient use of processing resources, it does tend to increasethe difficulty of identifying and addressing physical processingresource failures and maintenance since there is little available directrelationship between difficulties in performing processing functions anddifficulties with underlying physical processing resources.

One advantage of cloud computing and other virtualized networkingtechniques is that server information handling systems become blackboxes that can fit into server racks as needed to replace broken serversystems or to expand processing capabilities available for virtualsystems. Information technology administrators often work on data centerfloors to address physical resource maintenance and replacementindependent of functional resources running over the informationhandling systems. Once a server information handling system is repairedor replaced at a rack slot, the information technology administratorpowers the server up and configures the server to interact with themanagement and functional network resources. After the serverinformation handling system is under the control of administrative toolsthrough the management network, remote management controls are typicallyeffective to return the server information handling system into the poolof functional resources.

One difficulty with maintenance and replacement of server informationhandling systems is that information technology administrators mustcorrectly identify server information handling systems in the datacenter that have faults and need replacement or maintenance. Typically,information technology administrators in a data center will move a“crash” cart between server racks to investigate issues indicatedlocally by LED lights or small LED panels, or indicated remotely bycommunications from BMCs to administration tools. Once issues arespotted, the information technology administrator will typicallyinterface to the BMC locally with a USB or other cable interface inorder to retrieve detailed information regarding the fault and determinean appropriate corrective action. Generally, the information technologyadministrator fills out a trouble ticket based upon the indicated faultand submits the trouble ticket to an administrative tool to schedulemaintenance, such as replacement of failed components or of the serverinformation handling system. One difficulty with tracking failures bytrouble tickets is that complicated identification information and errorcodes can sometimes lead to errors at the input of trouble ticketinformation. Another difficulty that sometimes arises is that a deadserver information handling system is unavailable to provide informationat the data center floor related to the failure. For example, a completefailure of a server information handling system and its BMC is typicallyanalyzed by removal of the server information handling system for postmortem outside of the data center room.

SUMMARY OF THE INVENTION

Therefore a need has arisen for a system and method which supportsautomated issue identification, tracking and resolution proximate aserver information handling system housing.

A further need exists for a system and method that provides faultinformation proximate a server information handling system housing inthe event of power failure.

In accordance with the present invention, a system and method areprovided which substantially reduce the disadvantages and problemsassociated with previous methods and systems for server informationhandling system management and/or maintenance. An NFC device interfacedwith a server information handling system management controller providesfault codes detected by the management controller to a portableinformation handling system, such as a mobile telephone, for automatedgeneration of trouble tickets to report the fault. Faults are maintainedfor access by the NFC device even in the event of power failure by abackup battery that powers memory storing the fault codes that isinterfaced with the NFC device.

More specifically, plural server information handling systems deployedin proximity to each other, such as in a common rack or data center,each have an NFC device interfaced with a management controller, such asa baseboard management controller, that detects and reports faultsassociated with the server information handling system. As faults aredetected, the BMC logs the faults in memory accessible by the NFCdevice. An information technology administrator obtains the faults by anNFC transaction to the NFC device with a portable information handlingsystem, such as a smartphone. If the fault results in power failure, abackup battery maintains the fault information in memory. An applicationrunning on the smartphone automatically completes a trouble ticket formwith the information provided by the NFC transaction and reports thetrouble ticket to an administrative tool. The administrative tool issuesservice tickets that direct corrective actions coordinated by NFCtransactions. For example, a service ticket issued to a smartphonedirects an information technology administrator to repair the serverinformation handling system with a selected part. NFC transactionsbetween the selected part, the server information handling system andthe smartphone ensure that the correct part is placed in the correctserver information handling system with the correct configurationinformation. If a server information handling system replacement isspecified in a service ticket, then a removable bezel that integratesthe NFC device is removed from the failed server and placed on thereplacement server to aid in the transfer of configuration informationstored in tag memory of the NFC device. Unique identifiers of the serverinformation handling systems are referenced to ensure that configurationinformation on a bezel does not transfer to an incorrect server. If abezel is placed on a server that does not match a unique identifierstored in the bezel's NFC device, then the NFC tag is wiped clean.

The present invention provides a number of important technicaladvantages. One example of an important technical advantage is that aninformation technology administrator is able to obtain managementinformation when proximate a server information handling system housingby an NFC transaction to a portable information handling system, such asa smartphone. Configuration and identification information of the serverinformation handling system along with fault codes are automaticallypassed by NFC transaction to a portable information handling system sothat trouble tickets are quickly and accurately generated. Further,fault codes are maintained in RAM with a standby battery so that NFCtransactions include the final available fault codes detected at systempower failure. An information technology administrator who reads faultcodes from a failed system may sometimes be able to take correctiveaction on the installed system without performing a replacement, thusreducing disruptions to data center operations. NFC capabilities on aBMC and also replaceable components helps to ensure that authentic andauthorized repair components are installed in response to a troubleticket, thus reducing the risk that corrective actions will result inadditional maintenance issues. For example, a service ticket generatedin response to a trouble ticket embeds credentials based upon the NFCtransaction that generated the trouble ticket so that the correct serverinformation handling system is serviced with the correct replacementcomponents by the correct technician. In one embodiment, the NFC deviceis included in a bezel that selectively attaches to a server informationhandling system so that configuration information remains with a bezelwhen the bezel is removed from a server information handling system. Thebezel NFC erases configuration information if an identifier of a serverinformation handling to which the bezel attaches changes to anunexpected value, thus limiting the risk that incorrect configurationinformation will be applied to a server information handling system.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention may be better understood, and its numerousobjects, features and advantages made apparent to those skilled in theart by referencing the accompanying drawings. The use of the samereference number throughout the several figures designates a like orsimilar element.

FIG. 1 depicts a block diagram of a system for automated trouble ticketreporting at a server information handling system with an NFCtransaction;

FIG. 2 depicts a system for NFC transactions of server informationhandling system failure codes at power failure;

FIG. 3 depicts a flow diagram of a process for automated generation of aserver information handling system trouble ticket with an NFCtransaction;

FIG. 4 depicts a flow diagram of a process for providing serverinformation handling system fault codes in the event of a power failure;

FIG. 5 depicts a flow diagram of a process for transferringconfiguration information with a server information handling systembezel having an integrated NFC device;

FIG. 6 depicts a flow diagram of a process for authentication or areplacement component at a server information handling system BMC withan NFC transaction from the replacement component to the BMC;

FIG. 7 depicts a flow diagram of a process for configuration of areplacement component with NFC transactions through a mobile telephone;and

FIG. 8 depicts a flow diagram of a process for configuration of areplacement component by a BMC with NFC transactions through a mobiletelephone.

DETAILED DESCRIPTION

An NFC device with battery back-up disposed in a server informationhandling system bezel provides automated trouble ticket reporting andresponse even in the event of power failure at the server informationhandling system. For purposes of this disclosure, an informationhandling system may include any instrumentality or aggregate ofinstrumentalities operable to compute, classify, process, transmit,receive, retrieve, originate, switch, store, display, manifest, detect,record, reproduce, handle, or utilize any form of information,intelligence, or data for business, scientific, control, or otherpurposes. For example, an information handling system may be a personalcomputer, a network storage device, or any other suitable device and mayvary in size, shape, performance, functionality, and price. Theinformation handling system may include random access memory (RAM), oneor more processing resources such as a central processing unit (CPU) orhardware or software control logic, ROM, and/or other types ofnonvolatile memory. Additional components of the information handlingsystem may include one or more disk drives, one or more network portsfor communicating with external devices as well as various input andoutput (I/O) devices, such as a keyboard, a mouse, and a video display.The information handling system may also include one or more busesoperable to transmit communications between the various hardwarecomponents.

Referring now to FIG. 1, a block diagram depicts a system for automatedtrouble ticket reporting at a server information handling system 10 withan NFC transaction. Information handling systems 10 depicted by theexample embodiment of FIG. 1 are co-located in a common rack 12 witheach server information handling system 10 inserted in a slot 14 thatprovides power, cooling and wired networking infrastructure. Each serverinformation handling system 10 processes information with componentsdisposed on a motherboard 16, such as one or more central processingunits (CPUs) 18 that executes instructions, random access memory (RAM)20 that stores instructions and information, a chipset 22 that includesfirmware to coordinate actions between the processing components, a harddisk drive (HDD) 24 that provides persistent storage, and one or morenetwork interface cards (NICs) 26 that communicate with a wired network,such as Ethernet. Server information handling system 10 includes amanagement controller, such as a baseboard management controller (BMC)28, which provides remote management functions through a network 30. Forexample, BMC 28 allows an administrative tool 32 to perform remote powerup and power down as well as to perform maintenance, such as softwareand firmware patches. Administrative tool 32 tracks server hardware,software and security information with an administrative database 34.

During normal operations, plural racks disposed in a data center eachhave plural server information handlings 10 that process client requeststhrough network 30, such as the Internet. Operations of the serverinformation handling systems 10 are monitored by BMC's 28 for faults,such as failed components, reduced performance, thermal constraints andpower consumption. If a server information handling system 10 fails orhas a fault, a report is made to administrative tool 32 so that aninformation technology administrator can take corrective action, such aswith remote commands through BMC 28 or through physical interactionswith the server information handling system 10 on the datacenter floor.Server information handling systems also typically include visualindicators of faults that are managed by BMC 28, such as set of LEDs ora small display integrated with a chassis 36 that supports components ofthe server information handling system 10. In a typical scenario, aninformation technology administrator in a data center has a trouble cartwith tools and spare components to address failures in a prompt manneras the failures arise. The trouble cart may travel to racks 12 andserver information handling systems 10 based upon instructions sent fromadministrative tool 32 or may locate difficulties based upon visualindicators at a server information handling system 10, such as flashingLEDs. Once a server information handling system 10 is located with oneor more faults, the information technology administrator fills out a“trouble ticket” to report the fault to the administrative tool 32.Authorization to take actions in response to a trouble ticket is thenprovided with a “service ticket” from administrative tool 32, such as anauthorization to replace the server information handling system 10 orfaulty components in the server information handling system 10.

In order to simplify the completion of trouble tickets and responses toservice tickets, a mobile telephone information handling system 36 (orother portable information handling system, such as a tablet or laptop)interacts through NFC transactions supported by NFC devices 38 to managerepairs and replacements at server information handling systems 10.Mobile telephone information handling system 36 executes a faultapplication 40 to present a trouble and service ticket interface 42 at adisplay 44. An information technology administrator carries mobiletelephone information handling system 36 in the data center and respondsto fault indications provided by administrative tool 32 or by visualindicators, such as LED indications of faults. Once the informationtechnology administrator reaches the proximity of the server informationhandling system 10, placing NFC device 38 of mobile telephoneinformation handling system 36 proximate NFC device 38 of serverinformation handling system 10 results in an NFC transaction that passesfault information detected by BMC 28 to mobile telephone informationhandling system 36. For instance, a trouble ticket manager 48 passesfault codes detected by BMC 28 along with identification information ofthe server information handling system to fault application 40 of mobiletelephone 36. Fault application 40 accepts the fault information andautomatically fills out a trouble ticket to report the fault toadministrative tool 32. Since all of the information needed to completethe trouble ticket is passed by the NFC transaction, the trouble ticketis prepared and presented at trouble and service ticket interface 42without end user inputs. Once a trouble ticket is prepared, theinformation technology administrator is able to edit the trouble ticketif necessary and then send the trouble ticket to administrative tool 32.

Administrative tool 32 applies the trouble ticket to generate a serviceticket that provides the information technology administrator withauthorization and instructions for repairing or replacing the serverinformation handling system. For example, if a fault code indicates thata particular component has failed, the service ticket identifies areplacement component for use to replace the failed component, such asreplacement located on the crash cart of the information technologyadministrator assigned to fix the server information handling system.Alternatively, if the server information handling system has failed to apoint that the entire system needs replacement, the service ticketidentifies a replacement server information handling system 10, such asby a unique service identifier stored in the BMC of the replacementsystem. Administrative tool 32 sends the service ticket through awireless local area network (WLAN) 46 or a mobile telephone wirelesswide area network (WWAN) to the mobile telephone information handlingsystem 36 of the information technology administrator assigned toaddress the fault. The components addressed by the service ticket arestored in administrative database 34 to provide precise tracking byunique identifier of each server information handling system 10 and eachcomponent in the datacenter. Since unique identifiers are automaticallyloaded into trouble and service tickets, inadvertent errors due totypographical inputs are avoided.

When an information technology administrator approaches a serverinformation handling system 10 to address a service ticket, NFCtransactions between the server information handling system 10,replacement components and mobile telephone information handling system36 help to ensure that the correct repairs are performed. For example,if a hard disk drive is prescribed by the service ticket, an NFCtransaction between the hard disk drive and the mobile telephone ensuresthat the replacement component used by the information technologyadministrator matches that of the service ticket. Once the faultapplication obtains the replacement components information, another NFCtransaction between mobile telephone 36 and a server informationhandling system 10 allows transfer of the replacement componentinformation to the server information handling system. As anotherexample, an NFC transaction between the server information handlingsystem 10 BMC 28 NFC 38 and the replacement hard disk drive allows BMC28 to confirm the correct component and prepare configuration of the newhard disk drive. Similarly, an NFC transaction between the BMC 28 NFCdevice 38 and the failed hard disk drive allows BMC 28 to confirm thatthe correct hard disk drive was removed by the information technologyadministrator. As repairs are completed at a server information handlingsystem 10, administrative tool 32 updates administrative database 34 toreflect the changed system configurations as confirmed by NFCtransactions and BMC communications through network 30.

Referring now to FIG. 2, a system is depicted for NFC transactions ofserver information handling system 10 failure codes at power failure. Abezel 50 removably couples to server information handling system 10 sothat an information technology administrator is able to completelydetach bezel 50 and re-attach bezel 50. NFC device 38 is integrated withbezel 50, including an NFC transceiver 52 that performs NFC transactionsfrom and NFC tag memory 54. NFC device 38 when detached from serverinformation handling system 10 supports NFC transactions without powerby using a requesting device's RF energy to transmit information storedin persistent flash memory of NFC tag memory 54. NFC device 38interfaces with an NFC support circuit 56 that is integrated with serverinformation handling system 10. For example, NFC support circuit 56 is amicrocontroller that integrates RAM and flash memory as disclosed ingreater detail in U.S. patent application Ser. No. 14/259,574, entitled“NFC Communication with an Information Handling System Supplemented by aManagement Controller and Advertised virtual Tag Memory,” by Shawn Dubeand Syed S Ahmed, filed Apr. 23, 2014, which is incorporated herein byreference as if fully set forth. For example, NFC device 38 and NFCsupport circuit 56 communicate through a serial interface that snapsinto place when bezel 50 couples to server information handling system10. NFC support circuit interfaces with BMC 28 to receive faultinformation and provide enhanced NFC transactions, such as with avirtual tag memory supported by RAM integrated within NFC supportcircuit 56. During normal operations, NFC support circuit 56 is powerunder management of BMC 28, however, if BMC 28 does not have power, thena back-up battery 58 provides power to NFC support circuit 56 so that itmay continue to support NFC device 38.

One advantage of removable bezel 50 is that configuration informationfor server information handling system 10 is stored locally inpersistent NFC tag memory 54 to allow more rapid and accurateconfiguration of replacement server information handling system. Forexample, if a service ticket calls for replacement of a serverinformation handling system 10, the information technology administratorremoves bezel 50 from the installed server information handling systemand places bezel 50 on the replacement server information handlingsystem. When the replacement server information handling system 10powers up, its BMC 28 queries NFC support circuit 56 to findconfiguration information, if any, stored in NFC tag memory 54. If NFCtag memory 54 includes configuration information, then BMC 28 appliesthe configuration information to configure server information handlingsystem 10. Storage in bezel 50 of configuration information, such asnetwork addresses, boot order, etc. . . . , allows an informationtechnology administrator to coordinate configuration of serverinformation handling systems 10 interacting with a network before bezels50 are installed, thus reducing the time spent in a datacenter deployingnew or repaired systems. In order to confirm that a bezel 50 isconnected with an intended server information handing system 10, aunique identifier, such as service identifier 60, is stored with theconfiguration information. If BMC 28 retrieves configuration informationfrom NFC device 38, then BMC compares the service identifier 60retrieved with the configuration information to the BMC's own serviceidentifier to confirm that the bezel is intended to couple to serverinformation handling system 10. In one embodiment, NFC support circuit56 compares the service identifier 60 stored in NFC tag memory 54 withthe service identifier 60 of BMC 28 and erases the configurationinformation if the service identifiers 60 do not match. If a replacementserver information handling system 10 is installed and intended toaccept the stored configuration information, then an NFC transactionfrom mobile telephone 36 provides the replacement service identifier 60to the NFC tag so that a transfer of existing configuration informationis permitted.

On advantage of back-up battery 58 that powers NFC support circuit 56 isthat fault information is stored for access by NFC transactions evenafter failure of a server information handling system 10. For example,if power fails at server information handling system 10, thenpre-failure logic of BMC 28, such as logic running on reservecapacitance of the BMC circuit board, automatically saves all existingfault codes to memory of NFC support circuit 56. When an informationtechnology administrator approaches the failed server informationhandling system 10, he is able to retrieve fault codes with an NFCtransaction that accesses NFC support circuit 56 memory powered byback-up battery 58. Advantageously, NFC transaction access to faultcodes after power failure at server information handling system 10allows the information technology administrator to analyze a failureand, if possible, repair server information handling system 10 whilestill installed in the datacenter. Thus, a minor failure that results inpower down, such as a cooling fan or power supply failure, is repairedwithout the inconvenience and cost associated with removal andreplacement of the server information handling system.

Referring now to FIG. 3, a flow diagram depicts a process for automatedgeneration of a server information handling system trouble ticket withan NFC transaction. The process begins at step 62 with identification ofthe server information handling system having the fault, such as with aBMC notification to an administrative tool or a visual indication withLEDs seen by an information technology administrator on a datacenterfloor. At step 64, fault information, such as fault codes, are obtainedfrom the server information handling system with an NFC transaction to aportable information handling system held by an information technologyadministrator proximate to the server information handling system. Atstep 66, the fault information obtained through the NFC transaction isapplied at the portable information handling system, such as mobiletelephone, to automatically complete a trouble ticket on the portableinformation handling system. In one example embodiment, an applicationrunning on the portable information handling system requests informationby NFC transaction that is needed to fill out the trouble ticket. Inanother example embodiment, instructions running on the BMC or NFCsupport circuit have fields for the trouble ticket pre-completed andready to download upon request by an NFC transaction. In yet anotherexample embodiment, the NFC transaction instructs the BMC toautomatically generate a trouble ticket from the pre-completed fieldsand to send the trouble ticket through the BMC management network to theadministrative tool. In alternative embodiments, alternativeinstructions may be used to apply the fault codes and other serverinformation to complete an appropriate trouble ticket.

At step 68, the trouble ticket with the fault information and identifierfor the associated server information handling system 10 is sent to anadministrative tool. At step 70, corrective action in response to thefault code is authorized at the administrative tool, such as replacementof a failed component or server information handling system with areplacement component or server information handling system.Authorization of correction action may include specific actions andpredetermined components that the corrective action must include so thatthe repair has a reduced risk of causing problems in the operation ofthe datacenter. At step 72, credentials for performing the authorizedrepair are embedded in a service ticket and the service ticket isdispatched to initiate the corrective action. By issuing a serviceticket with credentials, such as an encrypted passcode also sent to theBMC that identifies the individual performing the repairs, access to theserver information handling system is selectively restricted, such aswith a bezel lock controlled by the BMC. At step 74, the credentials areconfirmed at the server information handling system with an NFCtransaction from a portable information handling system, such assmartphone. In one example embodiment, the credentials are based upon auser name and password of an information technology administratorassigned to perform the service. In another embodiment, the credentialsinclude a unique identifier for the server information handling systemunder repair and for each of the components authorized for use in therepair. Should a repair take place that differs from that authorized bythe service ticket, the administrative tool is notified and the serviceticket maintained open until the repair is completed as defined.

Referring now to FIG. 4, a flow diagram depicts a process for providingserver information handling system fault codes in the event of a powerfailure. The process begins at step 76 with detection of a fault at theserver information handling system, such as with logic running on a BMC.At step 78, the detected fault is logged as a fault code in memory ofthe NFC support circuit, such as by communicating fault codes as thecodes are detected to RAM in a microcontroller disposed between the BMCand NFC device. At step 80, a determination is made of whether the faulthas resulted in a failure of the server information handling system,such as a power failure that causes the BMC to power down. If not, thenthe process returns to step 76 to continue monitoring of the fault codesas the fault codes are detected. If a failure causes a power down atstep 80, the process continues to step 82 at which the memory of the NFCsupport circuit that stores fault codes is powered by the backupbattery. At step 84, the backup power provides NFC tag access to thefault codes in the NFC support circuit memory. An end user is thus ableto retrieve fault codes from a completely dead server informationhandling system by an NFC transaction supported with the backup battery.In one alternative embodiment, the backup battery provides power towrite the fault codes into persistent memory of the NFC tag so that thefault codes remain available even after the backup battery charge isexpended.

Referring now to FIG. 5, a flow diagram depicts a process fortransferring configuration information with a server informationhandling system bezel having an integrated NFC device. The processstarts at step 86 by attaching the bezel to the server informationhandling system so that the integrated NFC device communicates with theBMC, such as through a serial interface. At step 88, a comparison isperformed of the server information handling system unique identifiersstored on the BMC and in the NFC device integrated in the bezel. Thecomparison may be performed at the bezel with logic associated with theNFC device, at an NFC support circuit disposed between the BMC and NFCdevice or at the BMC. At step 90, a determination is made of whether theunique identifier stored on the NFC device, such as in the tag memory,matches a unique identifier of the server or servers allowed to couplewith the bezel. If the unique identifiers do not match, the processcontinues the step 92 to erase information stored in the tag memory ofthe NFC device. By erasing the tag memory where the bezel andinformation handling system unique identifiers do not match, assuranceis provided that configuration information stored in the tag memory willnot be applied to an unintended server information handling system. Ifthe unique identifiers match at step 90, the process continues to step94 to configure the information handling system with configurationinformation stored in the tag memory. In one example embodiment, a bezelremoved from a failed server information handling system has the uniqueidentifier of a replacement server information handling system stored inits tag memory by an NFC transaction so that the bezel provides theconfiguration information of the failed system to the replacement systemwhen the bezel is placed on the replacement system.

Referring now to FIG. 6, a flow diagram depicts a process forauthentication of a replacement component at a server informationhandling system BMC with an NFC transaction from the replacementcomponent to the BMC. The process starts at step 96 with detection of acomponents failure, such as by a BMC monitoring server operations or aninformation technology administrator walking datacenter to observe LEDindicators. At step 98, an NFC transaction is accomplished between anNFC device of the replacement component and a server informationhandling system BMC to provide the BMC with an identifier andconfiguration information for the replacement component, such as driversto incorporate the replacement component into the server. In oneembodiment, the replacement component is selected in a service ticketprovide from an administrative tool. At step 100, the replacementcomponent is authenticated with a server BMC by comparing theinformation received by the NFC transaction with expected information.For example, the BMC compares an identifier of the replacement componentwith an identifier indicated by a service ticket to ensure that thereplacement component is the correct part. As another example, the BMCcompares the type of replacement component with permissible types ofcomponents to ensure that the replacement component is compatible withthe server information handling system. At step 102, the BMC preparesthe server information handling system to accept the replacementcomponent, such as by loading any necessary drivers or adjusting anyconfiguration settings at the server based upon the information receivedby the NFC transaction. At step 104, the replacement component isinstalled in the server information handling system and supported by theBMC based upon the information provided from the replacement componentto the BMC by the NFC transaction. In one embodiment, physical access tothe server information handling system is restricted until installationis authorized by the BMC based upon the NFC transaction from thereplacement component to the BMC.

Referring now to FIG. 7, a flow diagram depicts a process forconfiguration of a replacement component with NFC transactions through amobile telephone. The process starts at step 106 with detection of acomponent failure at a server information handling system. At step 108,a replacement component for the failed component is installed in theserver information handling system. At step 110, an NFC transaction isperformed from the BMC to the mobile telephone of the replacementcomponent configuration as detected by the BMC. At step 112, theconfiguration of the replacement component is edited on the mobiletelephone to a desired configuration. At step 114, an NFC transaction isperformed from the mobile telephone to the BMC with the editedconfiguration information. At step 116, the server information handlingsystem applies the edited configuration information to configure thereplacement component. Advantageously, performing the configurationupdate in this manner allows completion of the configuration process andverification that the server is operating correctly before theinformation technology administrator leaves the location of the serverinformation handling system.

Referring now to FIG. 8, a flow diagram depicts a process forconfiguration of a replacement component by a BMC with NFC transactionsthrough a mobile telephone. The process starts at step 118 withdetection of a failure at a server information handling system. At step120, an NFC transaction is performed from the replacement component to amobile telephone to provide the mobile telephone with configurationinformation of the replacement component. At step 124, the replacementcomponent is installed in an information handling system. At step 126,an NFC transaction is performed from the mobile telephone to the serverBMC to provide the configuration information of the replacementcomponent to the BMC. At step 128, the BMC applies the configurationinformation to configure the replacement component to interact with theserver information handling system.

Although the present invention has been described in detail, it shouldbe understood that various changes, substitutions and alterations can bemade hereto without departing from the spirit and scope of the inventionas defined by the appended claims.

What is claimed is:
 1. A server information handling system comprising:a chassis; a processor disposed in the chassis and operable to executeinstructions that process information; memory disposed in the chassis,interfaced with the processor and operable to store the instructions andinformation; a management controller disposed in the chassis, interfacedwith the processor and non-transitory memory storing instructionsexecutable by the management controller to support remote managementfunctions including at least tracking faults by fault codes in amanagement controller memory, the management controller detecting powerfailures of the server information handling system and storing the faultcodes in the memory in response to the detecting the power failure; anear field communication (NFC) device interfaced with the managementcontroller and operable to communicate the fault codes with an NFCtransaction to an external NFC device; and a back-up battery interfacedwith the management controller memory and operable to power themanagement controller memory in the event of power failure so that themanagement controller memory provides access to the fault codes by theNFC device during power failure that prevents power to the managementcontroller.
 2. The server information handling system of claim 1 furthercomprising: an NFC support circuit interfaced with the battery, themanagement controller and the NFC device, the NFC support circuitoperable to run with power from the battery upon failure of the serverinformation handling system, the NFC support circuit providing the faultcodes stored in a management controller memory at the failure to the NFCdevice for communication by the NFC transaction to the external NFCdevice system.
 3. The server information handling system of claim 2wherein the battery is integrated with the NFC support circuit.
 4. Theserver information handling system of claim 2 wherein the battery isintegrated with the management controller.
 5. The server informationhandling system of claim 2 wherein the battery is integrated with theNFC device.
 6. The server information handling system of claim 1 furthercomprising: a bezel operable to couple to a front surface of thechassis; and an NFC support circuit having NFC support memory operableto store information in support of the NFC transactions; wherein the NFCdevice is integrated with the bezel and the NFC support circuit isoperable to cleanse the NFC support memory if an identifier associatedwith the NFC device fails to match an identifier associated with themanagement controller.
 7. The server information handling system ofclaim 6 wherein the NFC support memory stores configuration informationfor configuration of the server information handling system to interfacewith a network.
 8. The server information handling system of claim 7wherein the NFC device is further operable to accept an identifier of areplacement server information handling system to allow retention of theconfiguration information if the bezel transfers to the replacementinformation handling system.
 9. The server information handling systemof claim 1 wherein the management controller is further operable torequire identification information for a component by NFC transactionthrough the NFC device before authorizing installation of the component.10. A method for reporting server information handling system faults,the method comprising: detecting a fault at a server informationhandling system; storing a fault code associated with the fault inmemory accessible by an NFC device, the NFC device integrated with theserver; reading the fault code from the NFC device with an NFCtransaction after a power failure at the server information handlingsystem; detecting the power failure of the server information handlingsystem; and storing the fault code in the memory in response to thedetecting the power failure.
 11. The method of claim 10 wherein thememory comprises random access memory, the method further comprising: inresponse to the detecting the power failure, powering the random accessmemory with a back-up battery.
 12. The method of claim 11 furthercomprising: removing a bezel from the server information handlingsystem, the bezel including the NFC device; removing the serverinformation handling system from a support slot; inserting a replacementinformation handling system into the support slot; attaching the bezelto the replacement information handling system; and copyingconfiguration information from the NFC device to the replacementinformation handling system upon power up of the replacement serverinformation handling system.
 13. The method of claim 12 furthercomprising: performing an NFC transaction of an identifier of thereplacement server information handling system to the NFC device beforepowering up the replacement server information handling system;comparing the identifier with an identifier retrieved from thereplacement server information handling system upon power up of thereplacement server information handling system; and allowing the copyingconfiguration information only if the identifiers match.
 14. The methodof claim 12 further comprising: comparing an identifier stored on thereplacement server information handling system with an identifier storedon the NFC device; and disabling application of the configurationinformation at the replacement server information handling system if theidentifiers fail to match.
 15. The method of claim 14 further comprisingerasing the configuration information from the NFC device if theidentifiers fail to match.
 16. The method of claim 10 wherein detectinga fault indication at a server information handling system furthercomprises: detecting a power failure at the server information handlingsystem; and in response to detecting a power failure, storing the faultcode in memory accessible by an NFC device of the server informationhandling system when the server information handling system is powereddown.
 17. The method of claim 16 wherein the memory comprises a memorypowered by a back-up battery.
 18. A management subsystem for a serverinformation handling system, the management subsystem comprising: amanagement controller integrated with a chassis of the serverinformation handling system, the management controller operable tomanage operations of processing components disposed in the chassis, themanagement controller further operable to detect power failure and inresponse to detecting power failure to store fault codes in a memory; abezel operable to couple to the chassis; an NFC device integrated in thebezel and operable to perform NFC transactions with external NFCdevices; and an NFC support circuit disposed between the NFC device andthe management controller and having the memory, the memory storing thefault codes detected by the management controller in response todetecting power failure; wherein the NFC device is operable to providethe fault codes by NFC transaction to an external NFC device with themanagement controller powered off.
 19. The management subsystem of claim18 further comprising a battery interfaced with the NFC support circuitand operable to power the NFC support circuit when the managementcontroller is powered off, the NFC support circuit operable to providethe fault codes to the NFC device using battery power.